Skip to content

Conversation

@pawcoding
Copy link
Owner

@pawcoding pawcoding commented Sep 28, 2025

Planned release date

TBD

Issues

Changes

Features ✨

  • no new features

Fixes 🩹

  • Retry authentication with credentials after hitting rate limit

Internals 🛠️

  • Update docs to make recommendation for impersonateToken more visible
  • Update dependencies to latest versions
  • Schedule automatic test every week
    This ensures that we're always compatible with the latest PocketBase version
  • Upgrade to Node.js v24 since this is the new LTS version

Includes

  • nothing included

@pawcoding pawcoding self-assigned this Sep 28, 2025
@pawcoding
Copy link
Owner Author

🎉 This PR is included in version 2.8.2-next.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

@pawcoding pawcoding added the released on @next [bot] This is available in a pre-release label Oct 17, 2025
pawcoding and others added 4 commits October 17, 2025 20:19
This also fixes Astros content types to include the `rendered` property.

[skip ci]
@pawcoding
Copy link
Owner Author

🎉 This PR is included in version 2.8.2-next.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

pawcoding and others added 6 commits October 20, 2025 07:02
This only happens when your PocketBase instance has rate-limit
configured / your host enforces a rate limit. If enabled the
authentication is limited to 2 requests in 3 seconds, which the loader
will happily run into while generating schemas or fetching data
(especially with multiple collections being requested at the same time).

To prevent this, the auth request will now be retried with a random
backoff, though it's recommended to use an `impersonateToken` instead of
email and password credentials.

Other API endpoints for colleciton data fetching use higher rate limits,
so let's only tackle this once it actually becomes a problem.

Hopefully fixes #70
## [2.8.2-next.3](v2.8.2-next.2...v2.8.2-next.3) (2025-10-22)

### Bug Fixes

* **superuser-token:** retry authentication after hitting rate limit ([842c3e4](842c3e4)), closes [#70](#70)
@pawcoding
Copy link
Owner Author

🎉 This PR is included in version 2.8.2-next.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

released on @next [bot] This is available in a pre-release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants